Important: Subscriber Overcharging Protection is a licensed Cisco feature. A separate feature license may be required. Contact your Cisco account representative for detailed information on specific licensing requirements. For information on installing and verifying licenses, refer to the Managing License Keys section of the Software Management Operations chapter in the System Administration Guide.
Important: This section provides the minimum instruction set to configure the GGSN to avoid the overcharging due to loss of radio coverage in UMTS network. For this feature to be operational, you must also implement the configuration indicated in the section Overcharging Protection - SGSN Configuration also in this chapter. Commands that configure additional function for this feature are provided in the Cisco ASR 5000 Command Line Interface Reference.These instructions assume that you have already configured the system-level configuration as described in Cisco ASR 5000 System Administration Guide and the Cisco ASR 5000 Gateway GPRS Support Node Administration Guide.
|
Step 1
|
Configure the GTP-C private extension in a GGSN service by applying the example configurations presented in the GTP-C Private Extension Configuration section below.
|
|
Step 2
|
Save your configuration to flash memory, an external memory device, and/or a network location using the Exec mode command save configuration. For additional information on how to verify and save configuration files, refer to the System Administration Guide and the Command Line Interface Reference.
|
|
Step 3
|
Verify configuration of overcharging protection on LORC related parameters by applying the commands provided in the Verifying Your GGSN Configuration section in this chapter.
|
|
•
|
<vpn_context_name> is the name of the system context where specific GGSN service is configured. For more information, refer Cisco ASR 5000 Gateway GPRS Support Node Administration Guide.
|
|
•
|
<ggsn_svc_name> is name of the GGSN service where you want to enable the overcharging protection for subscribers due to LORC.
|
This section explains how to display and review the configurations after saving them in a .cfg file (as described in the Verifying and Saving Your Configuration chapter in this book) and how to retrieve errors and warnings within an active configuration for a service.
Important: All commands listed here are under Exec mode. Not all commands are available on all platforms.show ggsn-service name ggsn_svc_name
The output of this command displays the configuration for overcharging protection configured in the GGSN service ggsn_svc_name.
Important: This section provides a minimum instruction set to configure the SGSN to implement this feature. For this feature to be operational, you must also implement the configuration indicated in the section Overcharging Protection - GGSN Configuration also in this chapter.Command details can be found in the Cisco ASR 5000 Command Line Interface Reference.
|
•
|
the system-level configuration as described in the Cisco ASR 5000 System Administration Guide,
|
|
•
|
the SGSN service configuration as described in the Cisco ASR 5000 Serving GPRS Support Node Administration Guide, and
|
|
•
|
the configuration of an APN profile as described in the Operator Policy chapter in this guide.
|
|
Step 1
|
Configure the private extension IE with LORC in an APN profile by applying the example configurations presented in the Private Extension IE Configuration section.
|
Important: An APN profile is a component of the Operator Policy feature implementation. To implement this feature, an APN profile must be created and associated with an operator policy. For details, refer to the Operator Policy chapter in this book.|
Step 2
|
Configure the RANAP cause that should trigger this UPCQ message by applying the example configurations presented in the RANAP Cause Trigger Configuration section.
|
|
Step 3
|
Save your configuration to flash memory, an external memory device, and/or a network location using the Exec mode command save configuration. For additional information on how to verify and save configuration files, refer to the System Administration Guide and the Command Line Interface Reference.
|
|
Step 4
|
Verify the SGSN portion of the configuration for overcharging protection on LORC related parameters by applying the commands provided in the Verifying the Feature Configuration section.
|
|
•
|
<apn_profile_name> is the name of a previously configured APN profile. For more information, refer to the Operator Policy chapter, also in this book.
|
context <context_name>
iups-service <iups_service_name>
loss-of-radio-coverage ranap-cause <cause> end
|
•
|
<context_name> is the name of the previously configured context in which the IuPS service has been configured.
|
|
•
|
<cause> is an integer from 1 to 512 (the range of reasons is a part of the set defined by 3GPP TS 25.413) that allows configuration of the RANAP Iu release cause code to be included in messages. Default is 46 (MS/UE radio connection lost).
|
This section explains how to display the configurations after saving them in a .cfg file as described in the Verifying and Saving Your Configuration chapter elsewhere in this guide.
Important: All commands listed here are under Exec mode. Not all commands are available on all platforms.show apn-profile full name apn_profile_name
|
Step 2
|
show iups-service name <iups_service_name>
